Mvj 234 gdpr api #774
Merged
Mvj 234 gdpr api #774
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
juho-kettunen-nc
approved these changes
Nov 18, 2024
juho-kettunen-nc
approved these changes
Nov 19, 2024
henrinie-nc
force-pushed
the
MVJ-234-gdpr-api
branch
from
ea326fe to
0a6ab06
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds gdpr api package and configures it to work
Adds permission check for ensuring only suomi_fi users can access the gdpr api
Makes several related models
on_delete=models.SET_NULLin order to protect from cascaded deletion of these instances, in case the User model instance is deleted via GDPR APIThis currently just fetches data related to a user, deletion might require some additions e.g. marking which data can be deleted and what not.